Partially written block treatment

ABSTRACT

The present disclosure relates to partially written block treatment. An example method comprises maintaining, internal to a memory device, a status of a last written page corresponding to a partially written block. Responsive to receiving, from a controller, a read request to a page of the partially written block, the example method can include determining, from page map information maintained internal to the memory device and from the status of the last written page, which of a number of different read trim sets to use to read the page of the partially written block corresponding to the read request.

PRIORITY INFORMATION

This application is a Continuation of U.S. application Ser. No. 15/532,886 now U.S. Pat. No. 10,423,350, filed Jun. 2, 2017, which is a National Stage Application under 35 U.S.C. 371 of PCT/US2017/014535, filed Jan. 23, 2017, the contents of which are included herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to semiconductor memory and methods, and more particularly, to partially written block treatment.

BACKGROUND

Memory devices are typically provided as internal, semiconductor, integrated circuits in computers or other electronic devices. There are many different types of memory including volatile and non-volatile memory. Volatile memory can require power to maintain its data and includes random-access memory (RAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (SDRAM), among others. Non-volatile memory can provide persistent data by retaining stored data when not powered and can include NAND flash memory, NOR flash memory, read only memory (ROM), Electrically Erasable Programmable ROM (EEPROM), Erasable Programmable ROM (EPROM), and resistance variable memory such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), among others.

Memory devices can be combined together to form a storage volume of a memory system such as a solid state drive (SSD). A solid state drive can include non-volatile memory (e.g., NAND flash memory and NOR flash memory), and/or can include volatile memory (e.g., DRAM and SRAM), among various other types of non-volatile and volatile memory.

An SSD can be used to replace hard disk drives as the main storage volume for a computer, as the solid state drive can have advantages over hard drives in terms of performance, size, weight, ruggedness, operating temperature range, and power consumption. For example, SSDs can have superior performance when compared to magnetic disk drives due to their lack of moving parts, which may avoid seek time, latency, and other electro-mechanical delays associated with magnetic disk drives.

Data being written to memory cells can affect previously written data (e.g., via cell to cell interference). Accordingly, the charge corresponding to a programmed cell can be affected by whether or not neighboring cells have been programmed and/or by the particular programmed states of neighboring cells. Adjusting read parameters based on the program states of neighboring cells can provide benefits such as reducing bit error rates and/or reducing latency by preventing read re-tries (e.g., corrective reads), among various other benefits.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an apparatus in the form of a computing system including at least one memory system in accordance a number of embodiments of the present disclosure.

FIG. 2 is a block diagram of an apparatus in the form of a memory system configured to perform partially written block treatment in accordance with a number of embodiments of the present disclosure.

FIG. 3 illustrates an example of a memory unit having groups of memory cells organized as a number of physical blocks in accordance with a number of embodiments of the present disclosure.

FIG. 4 illustrates a diagram associated with programming memory cells in accordance with a number of embodiments of the present disclosure

FIG. 5 illustrates a table illustrating a number of different selectable read trim sets corresponding to different programming process page mapping types in accordance with a number of embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to partially written block treatment. An example method comprises maintaining, internal to a memory device, a status of a last written page corresponding to a partially written block. Responsive to receiving, from a controller, a read request to a page of the partially written block, the example method can include determining, from page map information maintained internal to the memory device and from the status of the last written page, which of a number of different read trim sets to use to read the page of the partially written block corresponding to the read request.

A number of embodiments of the present disclosure can provide benefits such as improving read performance of partially written blocks, as compared to prior approaches. For instance, treatment of partially written blocks in accordance with embodiments described herein can reduce uncorrectable bit error rates (UBERs), reduce the number of corrective reads, and also reduce complexity associated with system controllers (e.g., SSD controllers), among various other benefits. As described further herein, a partially written block refers to a physical block of memory configured to store a plurality of pages (e.g., logical pages) of data and which has not been fully written. In such cases, it can be useful to treat the last written page (e.g., the most recently written page) differently than previously written pages. For example, as described in association with FIGS. 3 and 4, the last written page may not belong to fully programmed cells (e.g., the cells storing the last written page may be configured to store three logical pages of data with the last written page corresponding to the first or second logical page). As one example, and as described in FIG. 4, the cells may be programmed via a two-pass programming process that comprises a first programming pass in which a lower page (LP) and a middle page (MP) are programmed to a group of memory cells, and a second programming pass in which an upper page (UP) is programmed to the group of cells. Additionally, the cells storing a last written page of a partially written block do not experience as much cell to cell interference (e.g., due to programming of neighboring cells) as cells storing previously written pages. Therefore, using the same read trim set (e.g., read voltage levels) to perform a read of a last written page of a partially written block as is used to perform a read of other pages can result in more read errors of the last written pages.

In the following detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how a number of embodiments of the disclosure may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the embodiments of this disclosure, and it is to be understood that other embodiments may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the present disclosure.

As used herein, “a number of” something can refer to one or more such things. For example, a number of memory devices can refer to one or more memory devices. Additionally, the designators “N”, “B”, “R”, and “S” as used herein, particularly with respect to reference numerals in the drawings, indicates that a number of the particular feature so designated can be included with a number of embodiments of the present disclosure.

The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. For example, 104 may reference element “04” in FIG. 1, and a similar element may be referenced as 204 in FIG. 2. As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. In addition, as will be appreciated, the proportion and the relative scale of the elements provided in the figures are intended to illustrate the embodiments of the present disclosure, and should not be taken in a limiting sense.

FIG. 1 is a block diagram of an apparatus in the form of a computing system 100 including at least one memory system 104 in accordance a number of embodiments of the present disclosure. As used herein, a memory system 104, a system controller (e.g., 215), a memory device (e.g., 210), or a device controller (e.g., 225) might also be separately considered an “apparatus”.

Computing system 100 includes a memory system 104 coupled to a host 102 through an interface 106. As used herein, “coupled to” generally refers to a connection between components, which may be an indirect communicative connection or direct communicative connection (e.g., without intervening components), whether wired or wireless, including connections such as, electrical, optical, magnetic, etc. The memory system 104 can be a solid state storage appliance implemented using a number of SSDs, for example. As described further in association with FIG. 2, the system 104 can include a system controller (e.g., 215) coupled to a memory (e.g., a number of memory devices 210-1, . . . , 210-N) via a suitable memory interface (e.g., 208).

Example hosts 102 can include laptop computers, personal computers, digital cameras, digital recording and playback devices, mobile telephones, PDAs (personal digital assistants), memory card readers, and interface hubs, among other host systems. The interface 106 can include a serial advanced technology attachment (SATA), peripheral component interconnect express (PCIe), or a universal serial bus (USB), among other connectors and interfaces. In general, however, host interface 106 can provide an interface for passing control, address, data, and other signals between the memory system 104 and the host 102.

Host 102 can include a number of processors 105 (e.g., parallel processors, co-processors, etc.) coupled to a memory and bus control 107. The processor 105 can be a number of microprocessors, or some other type of controlling circuitry, such as a number of application-specific integrated circuits (ASICs), for example. Other components of the computing system 100 may also have processors. The memory and bus control 107 can have memory and/or other components coupled thereto. In this example, memory and bus control 107 is coupled to a dynamic random access memory (DRAM) 11, a graphic user interface 118, and a peripheral and bus control 109. In this example, peripheral and bus control 109 is coupled to a flash drive 119 via a universal serial bus (USB) interface, a non-volatile memory host control interface (NVMHCI) flash memory 117, and the memory system 104. The memory system 104 can be used in addition to, or in lieu of, a hard disk drive (HDD) in a number of different computing systems. The computing system 100 illustrated in FIG. 1 is one example of such a system; however, embodiments of the present disclosure are not limited to the configuration shown in FIG. 1.

FIG. 2 is a block diagram of an apparatus in the form of a memory system 204 configured to perform partially written block treatment in accordance with a number of embodiments of the present disclosure. As one example, the memory system 204 can be a solid state drive (SSD). The memory system 204 includes a memory system controller 215 (e.g., memory control circuitry, firmware, and/or software) coupled to a memory (e.g., a number of memory devices 210-1, . . . , 210-N) via a bus 220. The memory devices 210-1, . . . , 210-N may be referred to collectively as memory devices 210 or as memory 210.

The system controller 215 includes a host interface 206 for communication with a host such as host 102 described in FIG. 1, and a device interface 208 for communication with the memory devices 210 via a bus 220. The bus 220 can send/receive various signals (e.g., data signals, control signals, and/or address signals) between the memory devices 210 and the system controller 215. Although the example illustrated in FIG. 2 includes a single bus 220, the memory system 204 can include a separate data bus (DQ bus), control bus, and address bus. The bus 220 can have various types of bus structures including, but not limited to, bus structures related to Open NAND Flash Interface (ONFI), Compact Flash Interface, Multimedia Card (MMC), Secure Digital (SD), CE-ATA, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), Firewire (IEEE 1394), and Small Computer Systems Interface (SCSI). The system controller 215 can be configured to support various data interface types associated with the memory devices 210 (e.g., NV-DDR, NV-DDR2, NV-DDR3, etc.).

The system controller 215 includes a translation component 216, which can be a flash translation layer (FTL), for example, associated with logical to physical address translation between the host and memory 210. For instance, the translation component 216 may include a mapping table of logical block addresses (LBAs) to physical block addresses (PBAs). Although not shown in FIG. 2, system controller might also include an error detection and/or correction component, a wear leveling component, and/or a garbage collection component, among various other components implemented in hardware, firmware, and/or software and associated with management of memory 210.

As illustrated in FIG. 2, the memory devices 210 can include a number of memory units 212-1, 212-2, 212-3, and 212-4, which may be referred to collectively as memory units 212 and which provide a storage volume for the memory system 204. The memory units 212 can be dies or chips, which can be referred to as logical units (LUNs). For example, the memory devices 210 can be multi-chip packages (MCPs) that each include a number of dies 212. The dies 212 can be, for example, NAND dies comprising a number of arrays of NAND flash memory cells and associated peripheral circuitry (e.g., write circuitry, read circuitry, I/O circuitry, buffers, etc.).

As described further below in association with FIGS. 3 to 5, the arrays can be NAND flash arrays comprising single level cells (SLCs) configured to store a single data unit (e.g., one bit), and/or multilevel cells (MLCs) configured to store more than one data unit. Additionally, the cells can be programmable via various different programming processes, which can depend on the quantity of data units stored per cell; however, cells configured to store a particular quantity of data units (e.g., 2 bits, 3 bits, 4 bits, etc.) per cell can be programmable via different programming processes. For example, a 3-bit MLC might be programmable via a two-pass programming process (e.g., a 4-8 process in which a first programming pass places the threshold voltage of the cells from an erase state into one of four distributions based on a lower page and middle page data state and in which a second programming pass places the threshold voltage of the cells from the one of four distributions into one of eight distributions based on the upper page data state), or a three-pass programming process (e.g., a 2-4-8 process).

Embodiments of the present disclosure are not limited to the example shown in FIG. 2. For instance, memory systems in accordance with embodiments of the present disclosure can include more or fewer than four memory units (e.g., die) 212 per memory device (e.g., MCP) 210 and are not limited to a particular memory array architecture (e.g., NAND flash, NOR flash, DRAM, PCM, etc.). Also, although one controller 225 is shown per device 210, embodiments can include a controller per memory unit 212 (e.g., one controller per NAND die).

The memory devices 210 of system 204 include an internal device controller 225 configured to control operations (e.g., read, program, erase, etc.) performed on the memory units 212 (e.g., responsive to commands from system controller 215 and/or from a host via system controller 215). The controllers 225 are local to the memory devices 210 and can communicate with the external system controller 215 via bus 220. As shown in FIG. 2, the internal device controllers 225 can use internally stored page map information 231, trim information 233, last written page (LWP) information 235, and partially written block (PWB) information 237, which can be used in association with partially written page treatment in accordance with embodiments described herein. As an example, the information 231, 233, 235, and 237 can be stored (e.g., as tables) in memory located on controller 225 and/or in the arrays of memory units 212. In a number of embodiments, maintaining the information 231, 233, 235, and/or 237 local to memory devices 210 can provide various benefits such as reducing the involvement of the system controller 215 in association with effectively reading partially written blocks as compared to previous approaches. For example, various previous approaches might involve the system controller sending a read request to a partially written block, receiving an uncorrectable error, and then re-reading the page corresponding to the read request with an adjusted trim set (e.g., via a corrective read). Such corrective reads can adversely affect latency. Other previous approaches to treating partially written blocks might involve the system controller 215 tracking which blocks of memory 212 are partially written as well as the last written page of the block, and the status of neighboring pages, which can have drawbacks such as increasing the complexity of the system controller (e.g., due to large table sizes, etc.).

As an example, the page map information 231 can comprise a programming order of pages written to the blocks. The programming order can include page numbers and can be used to determine the location of a particular page corresponding to a read request with respect to the page last written to the block. The last written page information 235 can provide a status of pages last written to partially written blocks, which can include identifiers (e.g., page numbers) of the last written pages and may also indicate a completion status of the last written page (e.g., whether the page belongs to a group of partially programmed cells, or whether the page is fully programmed). The last written page information 235 can be maintained on a per block basis (e.g., such that it includes the last written page information corresponding to all the individual partially written blocks). The completion status of the last written page may also be determined (e.g., by the controller 225) based on the page number of the last written page and the page map information 231. The partially written block information 237 can provide identifiers (e.g., block numbers) of partially written blocks (e.g., those blocks not yet programmed to completion). The trim information 233 can include different trim sets used to read pages of data responsive to read requests. As an example, a first trim set may be used to read pages written to cells that are not adjacent to cells to which the last written page was written, a second trim set may be used to read pages written to cells adjacent to unwritten cells, and a third trim set may be used to read pages written to cells that are adjacent to partially written cells.

In operation, memory device 210 can receive a write command (e.g., from system controller 215) that results in a particular block being partially written. The memory device 210 can store, internally, an indication that the particular block is a partially written block as well as an indication of the last written page to the partially written block. Prior to the remainder of the particular block being written, the memory device 210 can receive a read request (e.g., from system controller 215), which can include a block identifier (e.g., a particular physical block address) and a page identifier (e.g., a physical page number) associated with a requested page of data. The memory device 210 (e.g., via internal controller 225) can compare the received block identifier to the partially written block information 237 to determine whether the read request corresponds to a partially written block. Responsive to determining that the block identifier matches (e.g., that the read request corresponds to a partially written block), the internally stored page map information 231 and internally stored last written page information 235 can be used (e.g., by the internal controller 225) to determine which particular trim set 233 to select for reading the requested page (e.g., the page corresponding to the read request). In a number of embodiments, the memory device 210 can execute the read request corresponding to the partially written block using the appropriate trim set without further interaction with the system controller 215.

In a number of embodiments, the system controller 215 is unaware of the status of the last written page corresponding to the partially written block when sending the read request to the memory device 210. For instance, the controller 215 can be unaware that the requested page is a last written page of a partially written block. The read request sent from controller 215 to memory device 210 can be responsive to a host-initiated read request corresponding to a particular LBA, and the controller 215 can translate (e.g., via translation component 216) the LBA to a physical block address prior to sending the read request to the device 210. In a number of embodiments, the controller 215 may be configured to maintain a “shadow” copy of partially written blocks and/or last written pages within partially written blocks (e.g., such that system controller 215 and internal controller 225 maintain such information). In a number of embodiments, the system controller 215 can issue a command to the memory device 210 to read partially written block and/or last written page information from the device 210, which may enable the information to persist across power cycles, for example.

FIG. 3 illustrates an example of a memory unit 312 having groups of memory cells organized as a number of physical blocks 339-1 (BLOCK 1), 339-2 (BLOCK 2), . . . , 339-B (BLOCK B), in accordance with a number of embodiments of the present disclosure. The memory unit 312 can be a memory unit such as memory units 212 described in FIG. 2. The memory cells of memory unit 312 can be, for example, non-volatile floating gate flash memory cells having a NAND architecture. However, embodiments of the present disclosure are not limited to a particular memory type.

The memory blocks 339-1, 339-2, . . . , 339-B can be referred to collectively as blocks 339 and can comprise SLC and/or MLC cells, for instance. As an example, the number of physical blocks in an array of memory unit 312 may be 128 blocks, 512 blocks, or 1,024 blocks, but embodiments are not limited to a particular number of physical blocks.

In the example shown in FIG. 3, each physical block 339 includes memory cells which can be erased together as a unit (e.g., the cells in each physical block can be erased in a substantially simultaneous manner as an erase unit). As shown in FIG. 3, each physical block 339 comprises a number of physical rows 340-1, 340-2, . . . , 340-R of memory cells that can each be coupled to a respective access line (e.g., word line). The number of rows in each physical block can be 32, 64, or 128, but embodiments are not limited to a particular number of rows, which can be referred to collectively as rows 340, per block 339.

As one of ordinary skill in the art will appreciate, each row 340 can comprise a number of physical pages of cells. A physical page of cells can refer to a number of memory cells that are programmed and/or read together or as a functional group. In the embodiment shown in FIG. 3, each row 340 can comprise one physical page of cells. However, embodiments of the present disclosure are not so limited. For instance, each row 340 can comprise multiple physical pages of cells (e.g., an even page associated with cells coupled to even-numbered bit lines, and an odd page associated with cells coupled to odd numbered bit lines). Additionally, as described further in association with FIG. 4, for embodiments including multilevel cells, a physical page can store multiple logical pages of data with each cell in a physical page contributing a bit toward a logical lower page, a bit toward a logical upper page, and one or more bits toward a respective number of logical intermediate pages.

In the example shown in FIG. 3, a physical page corresponding to a row 340 can store a number of sectors 342-1, 342-2, . . . , 342-S of data (e.g., an amount of data corresponding to a host sector, such as 512 bytes). The sectors 342 may comprise user data as well as overhead data, such as error correction code (ECC) data and logical block address (LBA) data. It is noted that other configurations for the physical blocks 339, rows 340, and sectors 342 are possible. For example, rows 340 can each store data corresponding to a single sector which can include, for example, more or less than 512 bytes of data.

FIG. 4 illustrates a diagram associated with programming memory cells in accordance with a number of embodiments of the present disclosure. In this example, the memory cells are 3-bit MLCs each being programmable to one of eight data states (e.g., L1 to L8) assigned a different respective 3-bit bit pattern (e.g., 111, 011, 001, 101, 100, 000, 010, and 110). In a number of embodiments, each of the bits in the 3-bit stored bit patterns correspond to a different logical page of data. For instance, the least significant bit (LSB) (right most bit shown as boxed in FIG. 4) can correspond to a first page of data (e.g., a lower page), the middle bit can correspond to a second page of data (e.g., a middle page), and the most significant bit (MSB) (left most bit as indicated by a diamond symbol in FIG. 3) can correspond to a third page of data (e.g., an upper page).

However, embodiments are not limited to multilevel memory cells storing three bits of data. For instance, a number of embodiments can include memory cells configured to store more or fewer than three bits of data and/or a fractional number of bits of data per cell, and embodiments are not limited to the particular encoding assigned to the data states L1 to L8.

The diagram shown in FIG. 4 illustrates threshold voltage (Vt) distributions associated with programming memory cells (e.g., NAND flash cells) in accordance with a two-pass programming process (e.g., a 4-8 two-pass programming process) that includes a first programming pass (PP_1) 427 by which the lower page and middle page (LP/MP) are programmed, and a second programming pass (PP_2) 429 by which the upper page (UP) is programmed.

Threshold voltage (Vt) distribution 421 represents erased memory cells. The first programming pass 427 includes adjusting the Vt of the memory cells (e.g., via programming pulses applied to a selected word line) to one of four levels represented by Vt distributions 432-1, 432-2, 432-3, and 432-4. The voltage levels are represented by Vt distributions, which can reflect a statistical average Vt level of cells programmed to a particular level. In this example, cells whose lower page is to store a bit value of “1” (e.g., LP=1) and whose middle page is to store a bit value of “1” (e.g., MP=1) are programmed to distribution 432-1 during the first programming pass 427, cells whose lower page is to store a bit value of “1” (e.g., LP=1) and whose middle page is to store a bit value of “0” (e.g., MP=0) are programmed to distribution 432-2 during pass 427, cells whose lower page is to store a bit value of “0” (e.g., LP=0) and whose middle page is to store a bit value of “0” (e.g., MP=0) are programmed to distribution 432-3 during pass 427, and cells whose lower page is to store a bit value of “0” (e.g., LP=0) and whose middle page is to store a bit value of “1” (e.g., MP=1) are programmed to distribution 432-4 during pass 427.

The second programming pass 429 includes adjusting the Vt of the memory cells (e.g., via programming pulses applied to a selected word line) to one of eight levels represented by Vt distributions 434-1 to 434-8, which correspond to data states L1 to L8, respectively, with each one of data states L1 to L8 indicating a different 3-bit stored bit pattern. In this example, cells programmed to data state L1 store data “111,” cells programmed to data state L2 store data “011,” cells programmed to data state L3 store data “001,” cells programmed to data state L4 store data “101,” cells programmed to data state L5 store data “100,” cells programmed to data state L6 store data “000,” cells programmed to data state L7 store data “010,” and cells programmed to data state L8 store data “110.”

The diagram illustrated in FIG. 4 illustrates a number of read voltages 490-0, 490-1, 490-2, 490-3, 490-4, 490-5, and 490-6 (referred to generally as read voltages 490) associated with reading the bits of the three respective stored pages. A number of read strobes (e.g., using a number of the read voltages 490 applied to the selected word line) may be required in association with a reading a particular page of data. For instance, in this example, the encoding is such that a single read strobe (e.g., at read voltage 490-3) can be used to determine whether the lower page of the cell is a “0” or a “1” (e.g., a single Vt detection operation using read voltage 490-3). Also, in this example, two read strobes must be performed in order to decode the middle page (e.g., one strobe at read voltage 490-1 and one strobe at read voltage 490-5). Also, in this example, the encoding is such that four read strobes must be performed in order to decode the upper page (e.g., strobes at read voltages 490-0, 490-2, 490-4, and 490-6). However, in instances in which the first programming pass 427 has been performed but the second programming pass 429 has not been performed, it can be beneficial to use different read voltages to read the lower and middle pages than those read voltages (e.g., 490) used to read the lower and middle pages when the upper page has also been programmed. For example, if it is determined that the second programming pass 429 has not been performed, reading the lower page using read voltage 422-2 can result in fewer bit errors that using read voltage 490-3.

FIG. 5 illustrates a table 533 illustrating a number of different selectable read trim sets corresponding to different programming process page mapping types in accordance with a number of embodiments of the present disclosure. The table 533 is an example of trim information that can correspond to trim information 233 shown in FIG. 2. Column 551 illustrates four different programming process types, which can each have different corresponding page mappings.

For example, memory cells of memory units such as memory units 212 shown in FIG. 2 can be configured as SLC or MLC cells. The MLC configurations can be 2-bit, 3-bit, or 4-bit configurations, for instance. The page mapping (e.g., programming order of pages) can vary based on the particular MLC configuration. Additionally, the programming processes corresponding to a particular MLC can vary. For example, a 3-bit MLC configuration can be programmed in accordance with a one-pass, two-pass, or three-pass programming process. Accordingly, the read trim sets used to read a particular page can depend on the cell type (e.g., SLC or one of a number of different MLC types) as well as on the particular programming process used to program the page.

In addition, as described herein, it can be beneficial to adjust a particular trim set used to read a particular page depending on, for example, whether the particular page is a partially written page, whether the particular page is a last written page in a partially written block, and/or whether the particular page is adjacent to a last written page in a partially written block. In a number of embodiments of the present disclosure, an internal controller (e.g., 225) of a memory device (e.g., 210) can be configured to select, from among of a number of different read trim sets, an appropriate trim set for reading a particular page based on internally maintained page map information and internally maintained last written page status information.

In the example shown in FIG. 5, column 553 indicates a number of different trim sets corresponding to the respective programming process page mapping types shown in column 551. For instance, T1 can be a first trim set used to read SLCs of a last written page of a partially written block, and T2 can be a second trim set used to read SLCs of pages within a partially written block which are not the last written page or not adjacent to the last written page. T3, T4, and T5 can be trim sets used to read cells of type MLC1, which can correspond, for example, to 2-bit MLC cells programmed in accordance with a 2-4 two-pass programming process. T3 can be a first trim set used to read pages written to cells that do not store a last written page and are not adjacent to partially programmed cells storing the last written page, T4 can be a second trim set used to read pages written to cells that store the last written page and are adjacent to partially programmed cells (e.g., such that the last written page being read has experienced some interference due to programming of the adjacent cells), and T5 can be a third trim set used to read pages written to cells that store the last written page and are adjacent to unprogrammed cells (e.g., such that the last written page being read has not experienced interference due to programming of the unprogrammed adjacent cells).

T6, T7, and T8 can be trim sets used to read cells of type MLC2, which can correspond, for example, to 3-bit MLC cells programmed in accordance with a 4-8 two-pass programming process. T6 can be a first trim set used to read pages written to cells that do not store a last written page and are not adjacent to partially programmed cells storing the last written page, T7 can be a second trim set used to read pages written to cells that store the last written page and are adjacent to partially programmed cells, and T8 can be a third trim set used to read pages written to cells that store the last written page and are adjacent to unprogrammed cells. T9, T10, and T11 can be trim sets used to read cells of type MLC3, which can correspond, for example, to 3-bit MLC cells programmed in accordance with a 2-8 two-pass programming process. T9 can be a first trim set used to read pages written to cells that do not store a last written page and are not adjacent to partially programmed cells storing the last written page, T10 can be a second trim set used to read pages written to cells that store the last written page and are adjacent to partially programmed cells, and T11 can be a third trim set used to read pages written to cells that store the last written page and are adjacent to unprogrammed cells.

A number of embodiments of the present disclosure include maintaining page map information (e.g., 231) and trim information (e.g., 233) internal to a memory device (e.g., 210), which can provide various benefits. For example, the internal controller (e.g., 225) of the memory device can adapt to different programming process page mapping types without requiring reconfiguration information from an external controller (e.g., system controller 215 or a host such as host 102). For instance, since the internal controller can access page map information such as that shown in FIG. 5, the internal controller can select appropriate trims for reading partially written blocks for a variety of different cell types and/or programming process types without having to obtain additional trim settings from external sources, for instance.

Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results can be substituted for the specific embodiments shown. This disclosure is intended to cover adaptations or variations of a number of embodiments of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of a number of embodiments of the present disclosure includes other applications in which the above structures and methods are used. Therefore, the scope of a number of embodiments of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.

In the foregoing Detailed Description, some features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed embodiments of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

What is claimed is:
 1. A method comprising: maintaining a status of a last written page and page map information corresponding to a partially written block with a first controller internal to a memory device; performing, with a second controller that is external to the memory device, logical to physical address translation for the memory device; and determining, with the first controller without interaction with the second controller, a read trim set to use to read a page of the partially written block from the page map information and the status of the last written page.
 2. The method of claim 1, further comprising providing a read request for the page of the partially written block to the memory device, wherein the second controller is unaware that the read request corresponds to the partially written block.
 3. The method of claim 2, wherein providing the read request comprises providing a block identifier and a page identifier to the memory device.
 4. The method of claim 2, further comprising: providing the read request to the memory device responsive to a host-initiated read request corresponding to a particular logical block address; and translating, with the second controller, the particular logical block address to a physical block address prior to providing the read request to the memory device.
 5. The method of claim 1, wherein: the status of the last written page includes a page number corresponding to the last written page; and the page map information includes a programming order of pages written to the partially written block.
 6. The method of claim 1, wherein determining the read trim set comprises determining at least one of: whether memory cells to which the page is written are fully programmed; and a programming status of memory cells coupled to an access line adjacent to an access line to which the page is written.
 7. The method of claim 1, further comprising performing a read of the page of the partially written block using the determined read trim set without interaction with the second controller.
 8. The method of claim 1, wherein maintaining the page map information comprises maintaining page map information corresponding to a number of different programming process page mappings including at least two different two-pass programming process page mappings.
 9. The method of claim 1, further comprising: receiving, from the second controller, a write command to the memory device, wherein execution of the write command results in the partially written block; maintaining with the first controller an indication of the partially written block; receiving a read request from the second controller for the partially written block, wherein the read request includes a block identifier and a page identifier; comparing the block identifier to the indication of the partially written block; and responsive to determining that the block identifier matches the indication of the partially written block, determining the read trim set.
 10. An apparatus, comprising: a first controller internal to the memory device configured to maintain a status of a last written page corresponding to a partially written block; and a second controller external to a memory device configured to perform logical to physical address translation for the memory device, wherein the first controller is further configured to determine, from the page map information and the status of the last written page, a read trim set to use to read a page of the partially written block without interaction with the second controller.
 11. The apparatus of claim 10, wherein the second controller is a system controller of a solid state drive (SSD) and is coupled to the first controller internal to the memory device via a bus.
 12. The apparatus of claim 11, wherein the bus is associated with an Open NAND Flash Interface (ONFI) structure.
 13. The apparatus of claim 10, wherein the second controller does not track last written page information corresponding to pages of the memory device.
 14. The apparatus of claim 10, wherein the page map information includes a page programming order.
 15. The apparatus of claim 10, wherein: the status of the last written page includes a page number; and the first controller is configured to determine a location of the page relative to the last written page based on the page programming order.
 16. The apparatus of claim 10, wherein the status of the last written page corresponding to the partially written block includes a page identifier and an indication as to an amount of programming of the last written page.
 17. An apparatus, comprising: a memory device comprising: a plurality of blocks configured to store pages of data; and a first controller configured to maintain a status of last written pages corresponding to partially written blocks and page map information corresponding to partially written blocks; and a second controller coupled to a host via a host interface and externally coupled to the memory device via a device interface and configured to perform logical to physical address translation for the memory device, wherein the first controller is further configured to select a read trim set to read a page of data of a partially written block based on the status of the last written page and page map information corresponding to the partially written block without interaction with the second controller.
 18. The apparatus of claim 17, wherein the second controller is configured to provide a read request for the partially written block to the first controller.
 19. The apparatus of claim 18, wherein: the read request includes a block identifier and a page identifier; and the second controller is unaware of whether the block identifier corresponds to the partially written block when providing the read request.
 20. The apparatus of claim 17, wherein the page map information includes page maps corresponding to at least two different two-pass programming processes. 